Mobile device server

ABSTRACT

A mobile device server includes a flexible architecture having a plurality of components for allowing various mobile devices and protocols to communicate with each other and to receive data from various information spaces. Interface devlets send and receive messages in respective protocols. Access infolets utilize respective access methods to provide an abstract view of various information spaces. Logic applets implement service and/or application logic by processing information from one or more infolets. A further component referred to as a let engine communicates with the devlets, infolets, and applets, and maintains user and device profile information to provide a flexible framework for the mobile device server that can readily support new devices and protocols.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. patent application Ser. No.09/853,151, filed on May 10, 2001, which claims priority from U.S.Provisional Patent Application No. 60/248,816, filed on Nov. 15, 2000.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH

Not Applicable.

FIELD OF THE INVENTION

The present invention relates generally to communication systems and,more particularly, to portable wireless communication systems.

BACKGROUND OF THE INVENTION

As is known in the art, wireless Internet access is different fromsimply accessing the Internet wirelessly. Mobile wireless users havedifferent needs, motivations and capabilities from typical wirelineusers. For example, a mobile user is usually in a multi-tasking mode,e.g., accessing the Internet while attending a meeting or shopping inthe mall. Typical Internet accesses are bursty in nature (checking stockquotes, weather, or finding a nearby restaurant) and task-oriented.Thus, browser-centric applications and elaborate user interfaces are oflimited utility since a mobile user usually carries small devices suchas a cell phone or a Personal Digital Assistant (PDA) having relativelysmall displays. These personalized devices, which are typicallyidentified by a wireless network address such as a cellular phonenumber, provide mobile users with continuous access to the Internet.

Advances in wireless networking and messaging technologies have givenmobile users many choices to access Internet contents and services.Existing devices and protocols include PDAs, such as Palm Pilots withWeb Clipping, cell phones with wireless application protocol (WAP) orshort message service (SMS), email devices, such as Blackberry and AT&TPocketNet, supporting Post Office Protocol 3 (POP3) and/or (InternetMessage Access Protocol) IMAP, and America On Line (AOL) InstantMessaging (AIM).

While such devices and protocols can provide limited Internet access,differing devices and protocols do not communicate with each othereasily. Thus, business and individual mobile users must make challengingdecisions to obtain mobile access in a constantly changing environment.For example, employees of a particular company may need to use a singletype of device to enable wireless communication between the employees.However, one device type may not be optimal or desirable for the dutieseach employee must perform.

It would, therefore, be desirable to provide wireless communication fora variety of mobile device types and protocols. It would further bedesirable to provide wireless communication with a variety ofinformation spaces. It would also be desirable to readily supportwireless communication for new devices and protocols.

SUMMARY OF THE INVENTION

The present invention provides a mobile device server for providingcommunication with a variety of protocols and devices. The mobile deviceserver provides a message gateway for allowing mobile devices using arange of protocols and access networks to relay messages to each otherand to obtain information from a range of information spaces. With thisarrangement, a mobile user can readily communicate with other mobileusers having the same or different devices. A mobile user can alsoobtain data from a wide range of resources, such as the Internet anddatabases. While the invention is primarily shown and described inconjunction with portable mobile devices, it is understood that theinvention is generally applicable to systems in which it would bedesirable for differing device types and protocols to communicate witheach other.

In one aspect of the invention, a mobile device server includes aplurality of components that cooperate to enable a mobile device tocommunicate with other mobile device types and with a variety ofinformation space types. In one embodiment, a mobile device serverincludes an engine component that communicates with the mobile servercomponents and maintains user profile information. The server includes aplurality of interface components each of which corresponds to aparticular device type or protocol, for example. A plurality of accesscomponents provide abstract views of respective information spaces, suchas websites, databases, and corporate information. Each of a pluralityof logic components processes information retrieved by one or more ofthe access components for transmission back to the requesting mobiledevice via the corresponding interface component.

The engine component communicates with the interface, access and logiccomponents and maintains user/device profiles. In one embodiment, theengine component communicates with the interface components in apredetermined format, translates aliased user commands, invokesappropriate logic and access components, and transcodes retrieved datainto a format based upon characteristics, e.g., display size, of therequesting device.

In an exemplary operation, a mobile device issues a request for thelatest stock price of a particular company. The mobile device has aparticular messaging client, such as America On Line's Instant Messenger(AIM). The mobile device communicates with the mobile device server viaan AIM interface component, which receives the request for stock dataand formats the request into a predetermined format. The enginecomponent receives the formatted request, validates the mobile useridentification, and transforms command aliases, e.g., q for “quote”.

The engine component then sends the data request to an appropriate logiccomponent, which can for example, determine an optimum stock quoteservice based upon certain criteria. The logic component then requeststhe engine component to invoke the appropriate access componentcorresponding to the selected quote service, e.g., Yahoo. The accesscomponent then utilizes the proper mechanism, e.g., Hyper Text TransferProtocol (HTTP), to retrieve the requested content.

The retrieved raw content is returned to the engine component forexamination and formatting. The engine component accesses the profile ofthe recipient device to which the requested information is to be sent,which may or may not be the requesting mobile device. Based upon theprofile of the recipient device, the engine component invokes anappropriate access component for transcoding the retrieved raw contentinto the appropriate format, e.g., text only. The engine component thendelivers the transcoded data to the interface component corresponding tothe recipient device for transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be more fully understood from the following detaileddescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a schematic depiction of a mobile device server forcommunicating with a variety of devices and networks in accordance withthe present invention;

FIG. 2 is a schematic block diagram of an exemplary architecture for themobile device server of FIG. 1;

FIG. 3 is a schematic block diagram showing the mobile device serverhaving a plurality of interface devlets in accordance with the presentinvention;

FIG. 4 is a schematic depiction of an exemplary communication pathconfiguration for a mobile device server in accordance with the presentinvention;

FIG. 5 is a schematic block diagram showing the mobile device serverhaving a plurality of access infolets in accordance with the presentinvention;

FIG. 6 is a schematic block diagram showing a first part of a datatransfer by a mobile device server in accordance with the presentinvention;

FIG. 7 is a schematic block diagram showing a second part of a datatransfer by a mobile device server in accordance with the presentinvention;

FIG. 8 is a schematic block diagram showing a third part of a datatransfer by a mobile device server in accordance with the presentinvention;

FIG. 9 is a schematic block diagram showing a fourth part of a datatransfer by a mobile device server in accordance with the presentinvention;

FIG. 10A is an exemplary screen display showing Internet access offlight info from an AIM device through the AIM devlet on the mobiledevice server in accordance with the present invention;

FIG. 10B is an exemplary screen display showing website news access froma Palm V device through the email devlet on the mobile server inaccordance with the present invention;

FIG. 11A is an exemplary screen display for a device accessing acorporate database through the JDBC infolet on the mobile device serverin accordance with the present invention;

FIG. 11B is an exemplary screen display for a mobile phone accessing acorporate database through the JDBC infolet on the mobile device serverin accordance with the present invention;

FIG. 12 shows an exemplary screen display for a device requestingservice from a CORBA object through the AIM devlet on the mobile deviceserver in accordance with the present invention;

FIG. 13 is an exemplary screen display for a device controlling X10 homenetwork devices through the AIM devlet on the mobile device server inaccordance with the present invention;

FIG. 14 is an exemplary screen display for a device accessing an inboxof an E-mail account through the AIM devlet on the mobile device serverin accordance with the present invention;

FIG. 15 is a pictorial representation of an applet for finding a moviefor a mobile user of a mobile device server in accordance with thepresent invention; and

FIG. 16 is a schematic representation of an instant messaging mechanismfor a mobile device server in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In general, the present invention provides a mobile device server thatoperates as a message gateway for allowing mobile devices using variousprotocols on different access networks to communicate with each other.The mobile device server also allows mobile clients to access resourcesand information on the Internet and various other networks. The mobiledevice server includes a flexible architecture having a plurality ofcomponents that cooperate to service mobile device communicationrequests. Mobile device server components include a let engine componentcommunicating with interface devlets, logic applets, and accessinfolets. This arrangement allows the mobile device server to readilysupport new devices and protocols by adding corresponding devlets,infolets, and applets without altering the existing service logic.

As described more fully below, interface devlets receive and sendmessages through a particular protocol used by various mobile devices.Access infolets utilize particular access methods to provide an abstractview of respective information spaces. And access applets implementservice or application logic by processing information from one or moreinfolets. The let engine provides the basic framework for maintainingapplets, devlets and infolets, supporting user and device profiles forpersonalization and transcoding, and invoking proper applets andinfolets to answer data requests from devlets.

FIG. 1 shows an exemplary embodiment of a mobile device server 100 forenabling mobile users to communicate with a variety of devices andprotocols in accordance with the present invention. The mobile deviceserver 100 can run on a computer 102 having connections to a pluralityof networks and devices. It is understood that the mobile device servercan operate on a variety of known computers and operating systems, suchas Unix and Windows. In one embodiment, the mobile device server 100 isimplemented using the Java programming language running in a Windowsenvironment.

The mobile device server 100 further includes a mobile phone device 104for receiving and transmitting data via wireless communication. Themobile phone 104 can support Short Message Service (SMS) communication,which is well known to those skilled in the art. While shown as awireless phone coupled to the computer, it will be readily apparent toone of ordinary skill in the art that mobile device server functionalitycan be readily integrated into a single device. In addition, the mobiledevice server can include a number of wireless devices, which can be thesame or different type, coupled to the computer 102.

The mobile device server 100 enables communication between variousdevices and networks. In the illustrated embodiment, a cell phone 200with two-way short messaging service (SMS), e.g., a Global System forMobile Communication/Time Division Multiple Access (GSM/TDMA) phoneconnected to a GSM/TDMA network 202, can communicate with the mobiledevice server 100 through an SMS driver hosted on the mobile deviceserver. Cellular Digital Packet Data (CDPD) devices 204, such as AT&TPocketNet phone 204 a and Palm V 204 b, coupled to a CDPD network 206can use a Wireless Access Protocol (WAP) gateway 208 to access themobile device server 100 through the Internet 210. Email devices 214,such as a Blackberry mobile device, can use the Standard Email Protocol(SMTP) on the CDPD network 206 or a two-way paging network 216 coupledto a mail server 218 to communicate with the mobile device server 100.

In addition, PC device users and some PDAs can use AOL Instant Messenger(AIM) or web browsers to communicate with the mobile device server 100,which can support a Transmission Control Protocol (TCP) interface.Mobile devices can include an embedded module for communicating with themobile device server 100 directly via the TCP interface. The mobiledevice server 100 can receive messages and commands from these devices,access Internet services and information on behalf of a mobile user, andrelay messages or Internet content back to the sending devices or otherdevices, as described more fully below.

The mobile device server 100 includes an architecture having a pluralityof interface, logic, and access components that enable the mobile deviceserver to communicate with a range of devices, protocols and informationspaces. This arrangement hides the complexity of multiple devices andcontent sources from mobile users. The mobile device server 100 caninclude a proxy server that provides an environment for hosting agentsand personalized services, which can be implemented as reusable buildingblocks in the Java programming language, for example. An exemplary proxyserver known as iProxy, is shown and described in U.S. patentapplication Ser. No. 08/974,600, filed on Dec. 19, 1997, and Ser. No.09/474,914, filed on Dec. 30, 1999, which are incorporated herein byreference. In general, an iProxy agent, which can include a web-server,can be invoked like a regular common gateway interface (CGI) program.The iProxy system also allows scripts embedded inside web pages toinvoke agents to perform specialized processing. The iProxy systemmaintains user profiles and adds intelligence to the traditional HTTPproxy server to provide personalized, and value-added services such asfiltering, tracking, and archiving.

FIG. 2 shows an exemplary architecture for a mobile device server 300having a plurality of components that combine to provide a flexiblearchitecture that can readily support new devices, interfaces andinformation spaces. In one particular embodiment, the mobile deviceserver 300 includes interface devlets 302, logic applets 304 and accessinfolets 306. The devlet, infolet, and applets 302, 304, 306, as well asa proxy interface 308, communicate with each other through a let engine310. These components can be implemented as iProxy agents.

As shown in FIG. 3, each interface devlet 302 provides a protocolinterface to a given device on a particular access network. As describedabove, exemplary access network types include the Internet, CDPD, andGSM/TDMA, each of which is supported by one or more correspondinginterface devlets. In the illustrative embodiment, an AIM devlet 302 a,a GSM/TDMA devlet 302 b, a TCP/IP devlet 302 c, and a SMTP/IMAP devlet302 d are shown for communicating with the corresponding networks. It isunderstood that further interface devlets can be provided for a varietyof additional protocols well known to one skilled in the art. Forexample, email devlets can include SMTP, IMAP and POP3 devlets forsending and retrieving email.

The interface devlets 302 interact with the let engine 310 via apredetermined interface format. In one particular embodiment, thedevlets 302 provide requests to the let engine 310 in character-streamcommand lines and the let engine returns results in MultipurposeInternet Mail Extensions (MIME) format. After the mobile device server300 is initialized, each interface devlet 302 monitors a respectivechannel for incoming requests sent by a remote mobile device. Forexample, the AIM devlet 302 a on the mobile device server starts an AIMclient for listening to service requests from other AIM clients sent asinstant messages.

It is understood that the required device driver can form a part of acorresponding interface devlet 302 or can communicate with the devletthrough a TCP protocol, for example. This approach allows a devicedriver to run on a remote machine, i.e., a device other than on themobile device server.

FIG. 4 shows an exemplary communication path between an SMS mobilestation MS and a mobile device server MDS in accordance with the presentinvention. An SMS devlet running on the mobile device server MDScommunicates with a GSM cell phone MS attached to a remote personalcomputer RPC through an SMS driver. Mobile users can send messages tothe cell phone MS (through the GSM network), which then forwards eachmessage to the mobile device server MDS for processing. The mobiledevice server MDS then returns the result to the mobile user through thesame channel. Such an arrangement is further shown and described in U.S.Provisional Application No. 60/206,167 entitled “Mobile Phone InternetAccess Utilizing Short Message Service Method and Apparatus,” filed May22, 2000, which is incorporated by reference herein.

Similarly, to allow access to the mobile device server through email, amobile device server email devlet can monitor messages arriving at aparticular email account for new service requests. For TCP users, a TCPsession is created upon receiving a request to connect with a particularport of the mobile device server machine using the telnet protocol. Thetelnet user can enter mobile device server commands as if using atypical Unix or Windows terminal, for example. The mobile device servercan also support the WAP and HTTP protocols through the proxy interface308 (FIG. 2).

Referring again to FIG. 2, while each protocol and device can haveunique interfaces, each corresponding interface devlet 302 interactswith the let engine 310 in a predetermined format. More particularly, adevlet 302 can send a data request in the form of a character stream,interpreted as an mobile device server command and associatedparameters, to the let engine 310. The devlet 302 can receive resultsfrom the let engine 310 in a Multipurpose Internet Mail Extensions(MIME) format appropriate for the device, which is determined by thecorresponding device profile stored at the let engine. Device profilescontain information for user devices, such as how much information canbe displayed.

A simplified version of the mobile device server command syntax islisted below:

-   -   <command> := [ <forward_command> <destinations> ]        <applet_command> [ applet_argument> ]*<    -   destinations> := <destination> [ “,” <destination> ]*    -   <destination> := <protocol> “:” <account_id>        In this particular embodiment, the naming of each device or        destination follows the conventional URL naming scheme: protocol        name followed by an account name or address. For example,        typical destination addresses include “sms:+19735556242” (GSM        cell phone), “aim:sunshineX” (AIM buddy name),        “mail:iproxy@research.att.com (email id)”, etc.

As described more fully below, after receiving the command, the letengine 310 invokes one or more logic applets 304 that implement therequired logic for the data request. The let engine 310 then invokes theaccess infolet 306 appropriate for the information space to be accessed.

Referring briefly to FIG. 5, the access infolets 306 extend beyond theHTTP protocol and URL name space to provide abstract views of variousinformation spaces, such as databases 350, Internet information sources352, core networks 354, and X10 home devices. Corresponding accessinfolets, such as Java Data Base Connectivity (JDBC) 306 a, http 320 b,CORBA 306 c infolets access the respective information spaces as shown.A given interface infolet 306 retrieves information from a particularinformation space, such as stock quote sites, weather sites, and airlineflight databases. It is understood that the same information may beaccessed using a variety of access protocols. For example, suchinformation is commonly available on many websites, and may also beretrieved from XML files or databases. An interface infolet retrievesthe original content and returns it to an appropriate applet 304 forfurther processing, as described more fully below.

As an example of a mobile station request to access the stock price ofAT&T (stock symbol T), the mobile device user can issue a “quote T”command. If the request is sent by a mobile user using SMS on the GSMnetwork, then the result will be returned as plain text to therequesting GSM cell phone. If the mobile user wants to forward theresult to an email address, e.g., herman@research.att.com, the userissues a “forward mail:herman@research.att.com quote T” command. Sincethat email account understands the MIME type text/HTML (according to thedevice profile), the result will be sent by the let engine as an HTMLfile, complete with graphics, to the herman@research.att.com emailaccount.

The interface devlets 302 allow users on different networks to readilycommunicate with each other. For example, if a GSM phone user wants tosend a message to other devices, such as an AT&T PocketNet mail account,e.g., chen@mobile.att.net, which is on the CDPD network, and an AT&TTDMA phone having phone number 555-500-6531 using SMS, then an echoapplet can use a message relay service as follows: “forwardmail:chen@mobile.att.net, attmsg:5555006531 echo call your boss.”

FIGS. 6-9 show an exemplary transaction between a mobile device MS and amobile device server 300 in accordance with the present invention. Asshown in FIG. 6, the mobile device MS, such as a Palm Vx with a CDPDmodem having an AIM client, issues a “q T” (quote AT&T-stock symbol T)command, which requests that the mobile device server 300 retrieve thecurrent price of AT&T stock. The Palm Vx MS establishes a communicationchannel with the mobile device server 300 via an AIM devlet 302 a, e.g.,imobile4att. The AIM devlet 302 a receives the instant message from thePalm Vx device and formats the message into a predetermined format,e.g., “q T” in text, prior to passing the message to the enginecomponent or let engine 310. The engine component 310 transforms anyaliases, e.g., q for quote, defined by the mobile device user andauthenticates the user. The engine component 310 then invokes theappropriate logic applet 304 b, which can implement predetermined logicfor selecting a stock quote service, such as MSN, Yahoo, Etrade, etc.

As shown in FIG. 7, the logic applet 304 b then requests the let engine310 to invoke the appropriate, e.g., http, access infolet 306 a. In FIG.8, the access infolet 306 a retrieves the request stock informationusing the mechanism, e.g., http, appropriate for the selected quoteservice. The infolet 306 a then returns the raw data, which can be inHTML format, to the let engine 310.

As shown in FIG. 9, the let engine 310 examines the raw data, as well asprofile data for the recipient device, which can be the same ordifferent from the requesting mobile device MS. For example, the mobiledevice MS can request data to be forwarded to a specified device, suchas an email account. Based upon the profile of the recipient device, thelet engine 310 can send the raw data to a transcoding infolet 306 b forprocessing. In the case where the recipient device accepts only text inmessages less than 1000 bytes, the transcoding infolet 306 b transcodesthe raw data accordingly. After the infolet converts the data into text,the let engine 310 then delivers the text message to the AIM devlet 302a, if the Palm Vx device MS is the recipient device.

It is understood that the mobile device server of the present inventioncan communicate with a wide variety of mobile device types. In addition,the architecture of the mobile device server can readily support newfunctionality with applets, new devices with devlets, and newinformation spaces with infolets.

FIG. 10A shows an AIM client, mingfengchen, on an exemplary mobiledevice that talks to the mobile device server AIM agent, mfchen4iproxy.The AIM client issues the “flight 001” command to get flight informationon a particular airline and receives output including time and gateinformation for each leg of the flight. Mapping from the flight commandto the airline can be controlled by a corresponding logic appletaccording to the user profile. Also, the let engine invokes necessarytranscoding services to map the elaborate content on the airline websiteto the receiving device according to AIM device's profile.

FIG. 10B shows a Palm V device having an Omnisky modem that just sent anemail to the mobile device server email devlet atimobile@research.att.com with the command “sitenews att.” This commandinstructs the mobile device server to access the service provided byAT&T's Website News, which reports new hyperlinks on AT&T's website(http://www.att.com). The result is sent back as an email formatted forthe Palm V device.

FIG. 11A shows a mobile user connecting to an enterprise databasethrough an AIM client to find contact numbers for a particular softwareapplication using the mobile device server of the present invention.FIG. 11B shows how to access the same information from a cell phone thatsupports the WAP protocol. Corporate Information is typically accessedthrough JDBC and ODBC interfaces. The mobile device server includes aJDBC infolet that allows mobile users to access enterprise databaseinformation (marketing/sales data, system interface, etc.) throughSQL-like queries.

Network/Infrastructure Resources are typically accessed through theCORBA (Common Object Request Broker Architecture) interface. As known toone of ordinary skill in the art, CORBA is an architecture andspecification for managing distributed program objects in a network toallow programs at different locations to communicate through an“interface broker.” The mobile device server hosts a CORBA infolet thatallows mobile users to request services from CORBA objects. FIG. 12shows how an AIM user gets phone diversion information for the userHerman.

FIG. 13 shows a mobile device user controlling X10 devices remotely viathe mobile device server of the present invention. The X10 home networktechnology allows lamps and appliances connected on the same power lineto be controlled by a computer. The mobile device server hosts an X10infolet that controls home network devices connected to its servermachine. First, the user instructs the mobile device server to locatethe firecraker, the device that is capable of sending a radio signal toa transceiver device on the X10 network, through the serial port COM2 onthe mobile device server host. After the connection is established, acommand, e.g., “×10 on a1” is sent to turn on the fan (which is nameddevice a1 on that particular X10 network) and “×10 on a2” to turn on thecoffee pot. The X10 interface allows a mobile user to control thelighting and appliances at home with a GSM cell phone, an AIM client, oran email device anywhere in the world. The X10 infolet also demonstratesthat an infolet can be used to both retrieve and change the state of aninformation space. An applet based on X10 infolets can use an algorithmto determine when and how to activate certain X10 infolets to control ahome environment.

Further application for utilizing the mobile device server to accesshome network devices will be readily apparent to one of ordinary skillin the art. For example, motion sensors can be activated andde-activated using a mobile device, such as a cell phone. A user caninstruct a recording device to tape a television program using themobile device server. It is understood that a variety of devices can beused to access a home network. That is, a user can utilize any of a cellphone, PC, PDA, Palm device, etc. to manipulate home network devices. Itis further understood that while the mobile device server is primarilydescribed as supporting mobile devices, non-mobile devices such asdesktop PCs can communicate with the mobile device server.

FIG. 14 shows a mobile user accessing an email account via a mobiledevice server in accordance with the present invention. The mobile userfirst checks the status of the inbox to find the number of unreadmessages. The mobile device server supports an IMAP infolet called inboxthat can query and view a user's email account. The mobile user can lookat the size, e.g., 728 bytes, subject, and sender of that message beforeactually viewing it. Such interaction is advantageous for a mobile userwith limited bandwidth and screen space on a mobile device.

As described above, an applet implements business, service, orapplication logic by processing contents from different sources andrelaying results to various destination devices. A simple applet is the“echo” applet described above, which sends a message from one device toanother without using any information sources. It is understood that anapplet can also have relatively complex interactions with otherinfolets.

As showin in FIG. 15, for example, a FindMeAMovie applet can beimplemented as an iProxy script as shown below. #!/iproxy/script # getthe localtion information (zip) :javabin infoLet zip getlocation # gettop10 movies (mlist) :javabin infoLet mlist top10 movie :foreach mtitle${mlist} # Find theaters -- Movie: ${mtitle} -- :javabin infoLet thlistfindTheater ${mtitle} ${zip} :foreach theater ${thlist} # List the title& theater ${theater} :endfor :endforThis applet finds theaters near a cell phone user that are currentlyshowing the top ten movies by executing the following steps: 1) find outthe location (zip code) of the cell phone user, 2) find the top 10movies from a movie database or website, 3) for each of these movies,find out if any local theater shows that movie, and 4) list the movetitle and the theater.

In general, each devlet, infolet, and applet must be registered at thelet engine first before communications with other agents can occur. Eachabstract device that communicates with the mobile device server mustregister its profile information with the let engine first. A devicename is designated by protocol and account ID, i.e., protocol:acct_id.For example, an AIM user webciao is named aim:webciao. The mobile deviceserver maintains a default profile for each device type, and eachinstance of a device can overwrite that profile with device-specificinformation. A device profile can simply be a list of attribute-valuepairs. An important attribute is dev.format.accept, which determineswhat MIME type the device is allowed to accept. This information is usedby the mobile device server to transcode original content to a formatappropriate for this device, as described above. For example, thedefault profile for an email device is the following and can be namedmail.ini in the directory in which device profiles are kept:

-   -   dev.format.accept=text/html,*/*    -   dev.page.size=−1        The above device profile indicates that the default MIME type is        text/html, but all MIME types(*/*) are acceptable. Also, the        page size “−1” indicates that there is no limit on the size of        each message transmission. These values are inherited by all        mail devices unless they are overwritten. For example, while the        two default values might be valid for primary email devices        (desktop or laptop PC's), they are not appropriate for emails        used on cell phones, such as AT&T's PocketNet phone. The        following device profile for a PocketNet phone indicates that        only the MIME type text/plain is appropriate for this device and        that it does not accept messages longer than 230 characters:    -   dev.format.accept=text/plain dev.page.size=230

A devlet can require additional information that tells the mobile deviceserver how and when to access this device. For example, the followingprofile for the address imobile@research.att.com, used by the emaildevlet of the mobile device server, specifies the frequency (every 10seconds) of checking the email account (store.checktime), the accountpassword (store.url), the transport protocol for sending email(transport.url), last time the user accessed the account (cmd.lasttime),etc.

-   -   mail.store.checktime=10000    -   mail.store.url=imap://imobile:password@bigmail    -   mail.transport.url=smtp://bigmail    -   . . .

In general, each device is mapped to a registered user of the mobiledevice server. Significant reasons for this mapping arrangement includelimiting access to legitimate users of the mobile device server; andpersonalizing a service based on the user profile. An illustrativedevice-to-user map stored in the server (rarp.ini) is set forth below:

-   -   sms:+886935551826=herman    -   sms:+19085556842=chen    -   mail:dchang@research.att.com=difa    -   aim:webciao=chen . . .

It is understood that the mobile device server of the present inventioncan rely upon a variety of authentication techniques. Since the mobiledevice server interacts with multiple networks and protocols, the serverrelies on different authentication mechanisms. In one embodiment, themobile device server uses the cell phone identification on wirelessphone networks, AOL buddy names on the AIM network, and generic user IDand password information for WAP, HTTP, and telnet clients. However, themobile device server itself does not have control over the securityafforded by some of these networks. Alternative embodiments can includethe SSH Secure Shell to provide end-to-end authentication services. Ingeneral, the technique used by the mobile device server to authenticatea mobile user depends on the device or protocol used. Trusting wirelessnetworks, such as Voicestream/GSM and AT&T TDMA networks, to provide thecorrect cell phone id when a short message (SMS) is received isgenerally acceptable unless a cell phone is stolen and the user did notlock the phone with a security password. The mobile device server canalso trust the AOL network authentication for non-critical services.User authentication through the mobile device server itself is requiredif the user accesses the mobile device server through telnet, WAP, orHTTP. Following is a typical and simple user profile:

-   -   name=Robin Chen    -   password=xf2gbH3    -   default=$mail.1    -   # my addresses    -   sms.1=sms:+19085556842    -   mail.1=mail:chen@research.att.com    -   mail.2=mail:imobile@mobile.att.net    -   mail.all=$mail.1,$mail.2    -   aim.1=aim:webciao    -   # command aliases    -   sms.cmd.q=quote    -   sms.cmd.sn=sitenews    -   # address aliases    -   sms.addr.cc=aim:chrischen        This user profile stores the user name, password, and a list of        the devices that the user registers with the mobile device        server. It also stores command and address aliases. When a user        accesses the mobile device server through AIM using the id        webciao, the mobile device server determines from the        user-device map that the user is chen and uses the user profile        chen.ini for all later service requests from this device. For        example, the following short message sent from a GSM phone:        “forward $mail.1 q T” is interpreted as “forward        mail:chen@research.att.com quote T” according to the user        profile. The special character “$” requests that the mobile        device server map the named device, i.e., mail.1, to its        corresponding entry in the profile.

In a further embodiment, the mobile device server supports event drivenmessage generation to one or more users. In general, a user isconsidered to have previously requested such information when thepredetermined event occurs. For example, in the event that a child isabsent from school a message is sent to the parents cell phone. Themessage can be sent to a plurality of devices associated with the parentto ensure that the message is noticed. In addition, messages can beschduled for delivery at predetermined times. For example, a schedulerapplet can periodically check for scheduled events. For example, themobile device server can send a message to a device at a predeterminedtime to alert a person that a daily medication should be taken. It isunderstood that a user can be mapped to multiple devices in the userprofile. For example, a user can add to a daily journal located in a oneaddress location via multiple devices, such as a cell phone, PDA, andPC.

FIG. 16 shows an exemplary embodiment of mobile device server componentsfor supporting an instant messaging mechanism among a plurality ofdevices. In one embodiment, the instant messaging mechanism includes atalkto applet 400, a session ID applet 402, and a talkover applet 404.The talkto applet is invoked by the engine component 406 in response toa users request for instant messaging with another device, which can beof the same or different type. The engine component then generates thesession ID applet 402 for providing a session ID to each deviceparticipating in the instant messaging. The name of the appletcorresponds to the session ID, which is shared by the instant messagingusers. The talkover applet 404 terminates parties from the instantmessaging session. When all of the parties have left the session, thesession ID applet 402 ceases to exist.

One skilled in the art will appreciate further features and advantagesof the invention based on the above-described embodiments. Accordingly,the invention is not to be limited by what has been particularly shownand described, except as indicated by the appended claims. Allpublications and references cited herein are expressly incorporatedherein by reference in their entirety.

1. A mobile device server system for processing data requests from avariety of mobile device types, comprising: an engine component; aplurality of interface components communicating with the enginecomponent in a predetermined format, each of the plurality of interfacecomponents for providing a respective interface for mobile devicessending data requests; a plurality of access components communicatingwith the engine component, each of the plurality of access componentsfor providing an abstract view of a respective information source typebased upon the data requests; and a plurality of logic componentscommunicating with the engine component, each of the plurality of logiccomponents for processing information retrieved by the plurality ofaccess components and providing the processed information to one or moreof the plurality of interface components for transmission.
 2. The systemaccording to claim 1, further including a proxy interface for providinga communication interface to the mobile device server.
 3. The systemaccording to claim 1, wherein the plurality of interface componentsincludes components for supporting protocols selected from the groupconsisting of supporting interfaces to AIM, ICQ, SMS, XMS, Telnet, HTTP,WAP, SMTP, IMAP, POP3, and IVR.
 4. The system according to claim 1,wherein the plurality of access components includes components forproviding access to information spaces selected from the group of accesscomponents consisting of ODBC, JDBC, CORBA, http, X10, email, and XML.5. The system according to claim 1, wherein the predetermined formatincludes text for transfers from the plurality of interface componentsto the engine component.
 6. The system according to claim 5, wherein thepredetermined format includes MIME for transfers from the enginecomponent to the plurality of interface components.
 7. The systemaccording to claim 1, wherein the variety of mobile device types includedevices selected from the group consisting of SMS mobile phones, PDAdevices, Instant Messaging devices, Email devices, two way pagers,pocket PCs, and AT&T Pocket Net devices.
 8. The system according toclaim 1, wherein the mobile devices can communicate with one or more ofCDPD, TDMA, GSM, two way paging, Internet, and email networks.
 9. Thesystem according to claim 1, further including a logic component forre-directing the processed information to a further device associatedwith the first mobile device.
 10. The system according to claim 1,further including a logic component for scheduling an activation and/orresponse to a data request.
 11. A method for enabling communicationbetween a variety of mobile device types, comprising: receiving a firstdata request from a first mobile device utilizing a first protocol;receiving a second data request from a second mobile device utilizing asecond protocol; formatting the first and second data requests into apredetermined format; processing the first data request to initiate aninformation exchange between the first mobile device and a firstinformation space associated with a first information source; retrievingrequested data for the first data request from the first informationsource; formatting the retrieved data based upon parameters associatedwith the first mobile device; and sending the formatted data to thefirst mobile device using the first protocol.
 12. The method accordingto claim 11, further including supporting an additional type of mobiledevice by adding an interface component supporting the additional mobiledevice type.
 13. The method according to claim 11, further includingsupporting an additional type of information space by adding an accesscomponent supporting a protocol for accessing the additional type ofinformation space.
 14. The method according to claim 11, furtherincluding supporting an additional service function by adding a logiccomponent supporting the additional service.
 15. A method for adding newcomponents to a mobile device server having a flexible architecture,comprising: providing an engine component; providing a plurality ofinterface components communicating with the engine component in apredetermined format, each of the plurality of interface components forproviding a respective interface for mobile devices sending datarequests; providing a plurality of access components communicating withthe engine component, each of the plurality of access components forproviding an abstract view of a respective information source based uponthe data requests; providing a plurality of logic componentscommunicating with the engine component, each of the plurality of logiccomponents for processing information retrieved by the plurality ofaccess components and providing the processed information to one or moreof the plurality of interface components for transmission to the mobiledevice that sent the data request; and adding a further one of aninterface component, access component and a logic component to support arespective mobile device, information source, and process withoutaltering service logic of the mobile device server.
 16. A method forservicing data requests by a plurality of mobile device types,comprising: receiving a data request from a first mobile device via arespective one of a plurality of interface devlets; formatting the datarequest to a predetermined format; passing the formatted data request toa let engine; invoking at least one of a plurality of logic appletsbased upon the data request; invoking a respective one of a plurality ofaccess infolets based upon an information space type associated with thedata request; retrieving raw data from a device corresponding to theinformation space type; formatting the raw data based uponcharacteristics of a recipient device specified in the data request; andpassing the formatted the data to the recipient device via an interfacedevlet supporting the recipient device.
 17. The method according toclaim 16, further including formatting the data request into text. 18.The method according to claim 16, further including formatting the rawdata into MIME.
 19. The method according to claim 16, wherein thecharacteristics of the recipient device include a size limitation. 20.The method according to claim 16, further including servicing datarequests from devices including at least two device types selected fromthe group consisting of SMS mobile phones, Palm devices, AIM devices,AOL devices, two way pagers, pocket PCs, and AT&T Pocket Net devices.21. The method according to claim 16, further including supporting anadditional type of mobile device by adding a corresponding interfacedevlet without altering service logic.